release: 6.7.0 #2359
Merged
release: 6.7.0 #2359
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vaind
requested review from
adinauer,
romtsn,
stefanosiano and
markushi
as code owners
|
Sorry I didn't get, why do we need this? Isn't this already existing 78ede0b ? |
that commit is not on the main branch, unlike normal releases that haven't failed at some point in the release process, e.g. |
romtsn
approved these changes
Nov 14, 2022
|
@vaind gotcha, I enabled regular merge with a new commit creation - is that what you need? I think you can also use it |
thanks, can you approve it too? I can't merge otherwise |
|
I already approved, I guess it wants you to update the branch with latest |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a tagged release but not merged to the main branch - can anyone merge it without squashing (otherwise the release commit would say it doesn't exist in the repo?
#skip-changelog